-
Notifications
You must be signed in to change notification settings - Fork 488
separate T0 and V0 directory, V0 geometry and hits #1818
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
shahor02
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @AllaMaevskaya , please see a few comments below.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please leave the ACO last, just reassign T0=11, V0=12, FIT=13 and ACO=14
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And propagate the same to names
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
... and masks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do you nee o2::fit namespace declaration here? Below you use explicitly o2::fit::Digit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would remove the macros relying on the FairRunAna chain. The DPL digitizer-workflow should be used.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be sure: what is the reason to have common V0,T0 digits (under the fit namespace) and separate RecPoints?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in the HitType.h the HitType is defined in the o2::namespace, as well as in many places below.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Above the V0 derives its own Hit class directly from the BasicXYZEHit. If this class is for T0 only, why is it in the common dir.?
87f44e2 to
f95e36f
Compare
No description provided.